Adds the SMS/A2P 10DLC compliance language carriers require before a messaging campaign can be approved. Phone numbers and SMS consent are now disclosed in the Privacy Policy, and the Terms carry the standard CTIA program disclosures.

Privacy Policy (/privacy)

• New §4 "Phone Numbers & SMS Messaging" — discloses collection of mobile phone numbers, SMS opt-in/consent records, and message metadata; states messaging is transactional only.
• Carrier-required clause — mobile information and SMS opt-in/consent data are never sold or shared with third parties or affiliates for their own marketing purposes.
• Integrated for consistency with the existing document:
  • GDPR legal basis: consent now covers SMS, with STOP as the withdrawal path.
  • Data Retention: new line for phone number & SMS consent records.
  • Sub-Processors: generic "SMS delivery provider" entry (no provider named — none is verifiable in the repo yet; bound by an Art. 28 DPA).
• Subsequent sections renumbered (5–15); Last updated set to June 26, 2026.

Terms of Service (/terms)

• New §11 "SMS / Text Messaging Program" with the required disclosures:
  • Program is transactional only (verification codes, security alerts, service notifications).
  • Message frequency varies.
  • Message and data rates may apply.
  • Reply STOP to opt out (with one-time confirmation).
  • Reply HELP for help.
  • Carriers are not liable for delayed or undelivered messages.
  • Eligibility + link back to the Privacy Policy.
• Changes/Contact renumbered (12/13); Last updated set to June 26, 2026.

Notes for review

• Scope confirmed as transactional only (no marketing). If marketing messages are ever sent, the consent language must be upgraded to express written consent.
• SMS provider left unnamed in the sub-processor list — the only key in the repo is a SendGrid (email) key, so no SMS vendor is verifiable. Swap in the real provider name once confirmed.

Verification

• astro build succeeds; both pages render.
• check:plain coverage guard passes (privacy/terms intentionally have no plain twin).
• Confirmed all required phrases render in dist/terms.html and dist/privacy.html.
• Section numbering is sequential and gap-free on both pages.